Context-aware user interface (UI) for multi-form factor information handling systems (IHSs)

ABSTRACT

Embodiments of a context-aware User Interface (UI) for multi-form factor Information Handling Systems (IHSs) are described. In an illustrative, non-limiting embodiment, an IHS may include a processor and a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution by the processor, cause the IHS to: identify an arrangement of a second display relative to a first display; identify a position of a keyboard relative to the second display; and modify a Graphical User Interface (GUI) provided by the second display in response to: (i) the arrangement; and (ii) the position.

FIELD

This disclosure relates generally to Information Handling Systems (IHSs), and more specifically, to a context-aware User Interface (UI) for multi-form factor IHSs.

BACKGROUND

As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option available to users is Information Handling Systems (IHSs). An IHS generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. Because technology and information handling needs and requirements vary between different users or applications, IHSs may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in IHSs allow for IHSs to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, IHSs may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.

Nowadays, users can choose among many different types of mobile IHS devices. Each type of device (e.g., tablets, 2-in-1s, mobile workstations, notebooks, netbooks, ultra-books, etc.) has unique portability, performance, and usability features; however, each also has its own trade-offs and limitations. For example, tablets have less compute power than notebooks and workstations, while notebooks and workstations lack the portability of tablets. A conventional 2-in-1 device combines the portability of a tablet with the performance of a notebook, but with a small display—an uncomfortable form factor in many use-cases.

The inventors hereof have determined that, as productivity continues to be a core tenet of modern computing, mobile IHS devices should provide versatility for many use-cases and display postures in use today (e.g., tablet mode, laptop mode, etc.), as well as future display postures (e.g., digital notebooks, new work surfaces, etc.). Additionally, mobile IHS devices should provide larger display area with reduced size and weight.

SUMMARY

Embodiments of a context-aware User Interface (UI) for multi-form factor Information Handling Systems (IHSs) are described. In an illustrative, non-limiting embodiment, an IHS may include a processor and a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution by the processor, cause the IHS to: identify an arrangement of a second display relative to a first display; identify a position of a keyboard relative to the second display; and modify a Graphical User Interface (GUI) provided by the second display in response to: (i) the arrangement; and (ii) the position.

For example, the arrangement may be identified as a laptop posture, where the first display is at an obtuse angle with respect to the second display, and the second display is in a horizontal position with a display surface facing up. Alternatively, the arrangement may be identified as a tablet posture, where the first display is at a straight angle with respect to the second display, and the first and second displays are disposed in a horizontal position with first and second display surfaces facing up.

Alternatively, the arrangement may be identified as a book posture, where a first display surface of the first display is facing up, and a back surface of the first display is against a second display surface of the second display. Alternatively, the arrangement may be identified as a display posture, where: (a) the first display is at an acute angle with respect to the second display; or (b) a first display surface of the first display is at a straight or obtuse angle with respect to a second display surface of the second display, and the first and second displays are at a right angle with respect to a horizontal surface.

The program instructions, upon execution, may cause the IHS to determine that the keyboard is being placed above the second display, and modifying the GUI may include: resizing an application on the second display, or moving the application from the second display to the first display. Additionally, or alternatively, the program instructions, upon execution, may further cause the IHS to determine that the keyboard is placed atop a display surface of the second display, and where modifying the GUI may include: rendering a first bar on the second display along the keyboard. Additionally, or alternatively, the program instructions, upon execution, may further cause the IHS to identify a context of an application being executed by the IHS, where modifying the GUI may include adding a second bar to the first bar, and where the contents of the second bar are selected based upon the context.

Additionally, or alternatively, the program instructions, upon execution, may cause the IHS to determine that the keyboard is being moved from a first position on the display surface to a second position on the display surface, and modifying the GUI may include re-rendering the first bar at different locations on the second display as the keyboard moves. Additionally, or alternatively, the program instructions, upon execution, may further cause the IHS to determine that the keyboard is being moved from a higher position on the display surface to a lower position on the display surface, and modifying the GUI may include dynamically adding a second bar to the first bar.

Additionally, or alternatively, the program instructions, upon execution, may cause the IHS to determine that the keyboard is being moved from a lower position on the display surface to a higher position on the display surface, and modifying the GUI may include dynamically removing the second bar. Additionally, or alternatively, the program instructions, upon execution, may further cause the IHS to determine that the keyboard is being removed from the second display surface, and modifying the GUI may include moving or expanding an application window from the first display to the second display.

In some cases, modifying the GUI may include moving an Operating System (OS) taskbar from the first display to the second display. In other cases, modifying the GUI may include providing a virtual touchpad on a rectangular portion of a display surface of the second display below the keyboard. In yet other cases, modifying the GUI may include providing a scratch pad area below the keyboard and next to the touch input area.

The program instructions, upon execution, may cause the IHS to determine that the keyboard is off of a display surface of the second display, and modifying the GUI may include rendering a first bar alongside an edge of the second display in response to a selected key being pressed on the keyboard. Additionally, or alternatively, the program instructions, upon execution, may also cause the IHS to determine that a key is absent from the keyboard and render an image corresponding to the key on the second display. Additionally, or alternatively, the program instructions, upon execution, may further cause the IHS to determine that the keyboard is being moved from a higher position on the display surface to a lower position on the display surface, where modifying the GUI may include reducing the rectangular portion as the keyboard moves.

In another illustrative, non-limiting embodiments, a method may include identifying an arrangement of a second display relative to a first display; identifying a position of a keyboard relative to the second display; and modifying a GUI provided by the second display in response to: (i) the arrangement; and (ii) the position. In yet another illustrative, non-limiting embodiments, a hardware memory device may have program instructions stored thereon that, upon execution by a processor of an IHS, cause the IHS to: identify an arrangement of a second display relative to a first display; identify a position of a keyboard relative to the second display; and modify a GUI provided by the second display in response to: (i) the arrangement; and (ii) the position.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention(s) is/are illustrated by way of example and is/are not limited by the accompanying figures, in which like references indicate similar elements. Elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale.

FIG. 1 is a perspective view of a multi-form factor Information Handling System (IHS) with a removable keyboard, according to some embodiments.

FIGS. 2 and 3 are block diagrams of components of the multi-form factor IHS and removable keyboard, respectively, according to some embodiments.

FIG. 4 is a block diagram of a multi-form factor configuration engine, according to some embodiments.

FIG. 5 is a flowchart of a method for configuring multi-form factor IHSs, according to some embodiments.

FIGS. 6A-C, 7A-J, 8A-D, and 9A-F illustrate examples of laptop, tablet, book, and display postures, respectively, according to some embodiments.

FIGS. 10A-C and 11A-C illustrate various use-cases, according to some embodiments.

FIGS. 12A-D, 13A, and 13B illustrate a first hinge implementation and a second hinge implementation, respectively, according to some embodiments.

FIG. 14 illustrates an accessory charging system, according to some embodiments.

FIGS. 15, 16A-C, 17A, and 17B illustrate a third hinge implementation, a fourth hinge implementation, and a fifth hinge implementation, respectively, according to some embodiments.

FIGS. 18A and 18B illustrate a folio case system, according to some embodiments.

FIG. 19 illustrates an accessory backpack system, according to some embodiments.

FIGS. 20A and 20B are a flowchart of a method for providing context-aware User Interface (UI), according to some embodiments.

FIGS. 21A-C illustrate an example of a keyboard attachment and alignment system, according to some embodiments.

FIGS. 22A-D illustrate ribbon area and touch area UI components and operations, according to some embodiments.

FIGS. 23A and 23B illustrate OS components and UI operations, according to some embodiments.

FIG. 24 illustrates keyboard-initiated UI operations, according to some embodiments.

DETAILED DESCRIPTION

Embodiments described herein provide a context-aware User Interface (UI) for multi-form factor Information Handling Systems (IHSs). In various implementations, a mobile IHS device may include a dual-display, foldable IHS. Each display may include, for example, a Liquid Crystal Display (LCD), Organic Light-Emitting Diode (OLED), or Active Matrix OLED (AMOLED) panel or film, equipped with a touchscreen configured to receive touch inputs. The dual-display, foldable IHS may be configured by a user in any of a number of display postures, including, but not limited to: laptop, tablet, book, clipboard, stand, tent, and/or display.

A user may operate the dual-display, foldable IHS in various modes using a virtual, On-Screen Keyboard (OSK), or a removable, physical keyboard. In some use cases, a physical keyboard may be placed atop at least one of the screens to enable use of the IHS as a laptop, with additional User Interface (UI) features (e.g., virtual keys, touch input areas, etc.) made available via the underlying display, around the keyboard. In other use cases, the physical keyboard may be placed in front of the IHS to expose a larger display area. The user may also rotate the dual-display, foldable IHS, to further enable different modalities with the use of the physical keyboard. In some cases, when not in use, the physical keyboard may be placed or stored inside the dual-display, foldable IHS.

FIG. 1 is a perspective view of multi-form factor Information Handling System (IHS) 100 with removable keyboard 103. As shown, first display 101 is coupled to second display 102 via hinge 104, and keyboard 103 sits atop second display 102. The current physical arrangement of first display 101 and second display 102 creates a laptop posture, such that first display 101 becomes primary display area 105 presented by IHS 100, where video or display frames may be rendered for viewing by a user.

In operation, in this particular laptop posture, second display 102 may sit horizontally on a work surface with its display surface facing up, and keyboard 103 may be positioned on top of second display 102, occluding a part of its display surface. In response to this posture and keyboard position, IHS 100 may dynamically produce a first UI feature in the form of at least one configurable secondary display area 106 (a “ribbon area” or “touch bar”), and/or a second UI feature in the form of at least one configurable touch input area 107 (a “virtual trackpad”), using the touchscreen of second display 102.

To identify a current posture of IHS 100 and a current physical relationship or spacial arrangement (e.g., distance, position, speed, etc.) between display(s) 101/102 and keyboard 103, IHS 100 may be configured to use one or more sensors disposed in first display 101, second display 102, keyboard 103, and/or hinge 104. Based upon readings from these various sensors, IHS 100 may then select, configure, modify, and/or provide (e.g., content, size, position, etc.) one or more UI features.

In various embodiments, displays 101 and 102 may be coupled to each other via hinge 104 to thereby assume a plurality of different postures, including, but not limited, to: laptop, tablet, book, or display.

When display 102 is disposed horizontally in laptop posture, keyboard 103 may be placed on top of display 102, thus resulting in a first set of UI features (e.g., ribbon area or touch bar 106, and/or touchpad 107). Otherwise, with IHS 100 still in the laptop posture, keyboard 103 may be placed next to display 102, resulting in a second set of UI features.

As used herein, the term “ribbon area” or “touch bar” 106 refers to a dynamic horizontal or vertical strip of selectable and/or scrollable items, which may be dynamically selected for display and/or IHS control depending upon a present context, use-case, or application. For example, when IHS 100 is executing a web browser, ribbon area or touch bar 106 may show navigation controls and favorite websites. Then, when IHS 100 operates a mail application, ribbon area or touch bar 106 may display mail actions, such as replying or flagging. In some cases, at least a portion of ribbon area or touch bar 106 may be provided in the form of a stationary control strip, providing access to system features such as brightness and volume. Additionally, or alternatively, ribbon area or touch bar 106 may enable multitouch, to support two or more simultaneous inputs.

In some cases, ribbon area 106 may change position, location, or size if keyboard 103 is moved alongside a lateral or short edge of second display 102 (e.g., from horizontally displayed alongside a long side of keyboard 103 to being vertically displayed alongside a short side of keyboard 103). Also, the entire display surface of display 102 may show rendered video frames if keyboard 103 is moved alongside the bottom or long edge of display 102. Conversely, if keyboard 103 is removed of turned off, yet another set of UI features, such as an OSK, may be provided via display(s) 101/102. As such, in many embodiments, the distance and/or relative position between keyboard 103 and display(s) 101/102 may be used to control various aspects the UI.

During operation, the user may open, close, flip, swivel, or rotate either of displays 101 and/or 102, via hinge 104, to produce different postures. In each posture, a different arrangement between IHS 100 and keyboard 103 results in different UI features being presented or made available to the user. For example, when second display 102 is folded against display 101 so that the two displays have their backs against each other, IHS 100 may be said to have assumed a tablet posture (e.g., FIG. 7G) or book posture (e.g., FIG. 8D), depending upon whether IHS 100 is stationary, moving, horizontal, resting at a different angle, and/or its orientation (landscape vs. portrait).

In many of these scenarios, placement of keyboard 103 upon or near display(s) 101/102, and subsequent movement or removal, may result in a different set of UI features than when IHS 100 is in laptop posture.

In many implementations, different types of hinges 104 may be used to achieve and maintain different display postures, and to support different keyboard arrangements. Examples of suitable hinges 104 include, but are not limited to: a 360-hinge (FIGS. 12A-D), a jaws hinge (FIGS. 13A and 13B), a yoga hinge (FIG. 15), a gear hinge (FIGS. 16A-C), and a slide hinge (FIGS. 17A and 17B). One or more of these hinges 104 may include wells or compartments (FIG. 14) for docking, cradling, charging, or storing accessories. Moreover, one or more aspects of hinge 104 may be monitored via one or more sensors (e.g., to determine whether an accessory is charging) when controlling the different UI features.

In some cases, a folio case system (FIGS. 18A and 18B) may be used to facilitate keyboard arrangements. Additionally, or alternatively, an accessory backpack system (FIG. 19) may be used to hold keyboard 103 and/or an extra battery or accessory.

For purposes of this disclosure, an IHS may include any instrumentality or aggregate of instrumentalities operable to compute, calculate, determine, classify, process, transmit, receive, retrieve, originate, switch, store, display, communicate, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, or other purposes. For example, an IHS may be a personal computer (e.g., desktop or laptop), tablet computer, mobile device (e.g., Personal Digital Assistant (PDA) or smart phone), server (e.g., blade server or rack server), a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. An IHS may include Random Access Memory (RAM), one or more processing resources such as a Central Processing Unit (CPU) or hardware or software control logic, Read-Only Memory (ROM), and/or other types of nonvolatile memory. Additional components of an IHS may include one or more disk drives, one or more network ports for communicating with external devices as well as various I/O devices, such as a keyboard, a mouse, touchscreen, and/or a video display. An IHS may also include one or more buses operable to transmit communications between the various hardware components.

FIG. 2 is a block diagram of components 200 of multi-form factor IHS 100. As depicted, components 200 include processor 201. In various embodiments, IHS 100 may be a single-processor system, or a multi-processor system including two or more processors. Processor 201 may include any processor capable of executing program instructions, such as a PENTIUM series processor, or any general-purpose or embedded processors implementing any of a variety of Instruction Set Architectures (ISAs), such as an x86 ISA or a Reduced Instruction Set Computer (RISC) ISA (e.g., POWERPC, ARM, SPARC, MIPS, etc.).

IHS 100 includes chipset 202 coupled to processor 201. In certain embodiments, chipset 202 may utilize a QuickPath Interconnect (QPI) bus to communicate with processor 201. In various embodiments, chipset 202 may provide processor 201 with access to a number of resources. Moreover, chipset 202 may be coupled to communication interface(s) 205 to enable communications via various wired and/or wireless networks, such as Ethernet, WiFi, BLUETOOTH, cellular or mobile networks (e.g., CDMA, TDMA, LTE, etc.), satellite networks, or the like. For example, communication interface(s) 205 may be coupled to chipset 202 via a PCIe bus.

Chipset 202 may be coupled to display controller(s) 204, which may include one or more or graphics processor(s) (GPUs) on a graphics bus, such as an Accelerated Graphics Port (AGP) or Peripheral Component Interconnect Express (PCIe) bus. As shown, display controller(s) 204 provide video or display signals to first display device 101 and second display device 202. In other implementations, any number of display controller(s) 204 and/or display devices 101/102 may be used.

Each of display devices 101 and 102 may include a flexible display that is deformable (e.g., bent, folded, rolled, or stretched) by an external force applied thereto. For example, display devices 101 and 102 may include LCD, OLED, or AMOLED, plasma, electrophoretic, or electrowetting panel(s) or film(s). Each display device 101 and 102 may include a plurality of pixels arranged in a matrix, configured to display visual information, such as text, two-dimensional images, video, three-dimensional images, etc.

Display device(s) 101/102 may be configured to sense haptic and/or physical touch events, and to generate touch information. To this end, display device(s) 101/102 may include a touchscreen matrix (e.g., a layered capacitive panel or the like) and/or touch controller configured to receive and interpret multi-touch gestures from a user touching the screen with a stylus or one or more fingers. In some cases, display and touch control aspects of display device(s) 101/102 may be collectively operated and controlled by display controller(s) 204.

In some cases, display device(s) 101/102 may also comprise a deformation or bending sensor configured to generate deformation or bending information including, but not limited to: the bending position of a display (e.g., in the form of a “bending line” connecting two or more positions at which bending is detected on the display), bending direction, bending angle, bending speed, etc. In these implementations, display device(s) 101/102 may be provided as a single continuous display, rather than two discrete displays.

Chipset 202 may also provide processor 201 and/or display controller(s) 204 with access to memory 203. In various embodiments, system memory 203 may be implemented using any suitable memory technology, such as static RAM (SRAM), dynamic RAM (DRAM) or magnetic disks, or any nonvolatile/Flash-type memory, such as a solid-state drive (SSD) or the like. Memory 203 may store program instructions that, upon execution by processor 201 and/or controller(s) 204, present a UI interface to a user of IHS 100.

Chipset 202 may further provide access to one or more hard disk and/or solid-state drives 207. In certain embodiments, chipset 202 may also provide access to one or more optical drives or other removable-media drives. In certain embodiments, chipset 202 may also provide access to one or more Universal Serial Bus (USB) ports 208.

Upon booting of IHS 100, processor(s) 201 may utilize Basic Input/Output System (BIOS) 209 instructions to initialize and test hardware components coupled to IHS 100 and to load an Operating System (OS) for use by IHS 100. BIOS 209 provides an abstraction layer that allows the OS to interface with certain hardware components that are utilized by IHS 100. Via the hardware abstraction layer provided by BIOS 209, software stored in memory 203 and executed by the processor(s) 201 of IHS 100 is able to interface with certain I/O devices that are coupled to the IHS 100. The Unified Extensible Firmware Interface (UEFI) was designed as a successor to BIOS. As a result, many modern IHSs utilize UEFI in addition to or instead of a BIOS. As used herein, BIOS is intended to also encompass UEFI.

Chipset 202 may also provide access to one or more user input devices 206, for example, using a super I/O controller or the like. For instance, chipset 202 may provide access to a keyboard (e.g., keyboard 103), mouse, trackpad, stylus, totem, or any other peripheral input device, including touchscreen displays 101 and 102. These input devices may interface with chipset 202 through wired connections (e.g., in the case of touch inputs received via display controller(s) 204) or wireless connections (e.g., via communication interfaces(s) 205). In some cases, chipset 202 may be used to interface with user input devices such as keypads, biometric scanning devices, and voice or optical recognition devices.

In certain embodiments, chipset 202 may also provide an interface for communications with one or more sensors 210. Sensors 210 may be disposed within displays 101/102 and/or hinge 104, and may include, but are not limited to: electric, magnetic, radio, optical, infrared, thermal, force, pressure, acoustic, ultrasonic, proximity, position, deformation, bending, direction, movement, velocity, rotation, and/or acceleration sensor(s).

FIG. 3 is a block diagram of components 300 of keyboard IHS 103. As depicted, components 300 include keyboard controller or processor 301, coupled to keyboard sensor(s) 303 and wireless communication module 302. In various embodiments, keyboard controller 301 may be configured to detect keystrokes made by user upon a keyboard matrix, and it may transmit those keystrokes to IHS 100 via wireless module 302 using a suitable protocol (e.g., BLUETOOTH). Keyboard sensors 303, which may also include any of the aforementioned types of sensor(s), may be disposed under keys and/or around the keyboard's enclosure, to provide information regarding the location, arrangement, or status of keyboard 103 to IHS 100 via wireless module 302.

In various embodiments, IHS 100 and/or keyboard 103 may not include all of components 200 and/or 300 shown in FIGS. 2 and 3, respectively. Additionally, or alternatively, IHS 100 and/or keyboard 103 may include components in addition to those shown in FIGS. 2 and 3, respectively. Additionally, or alternatively, components 200 and/or 300, represented as discrete in FIGS. 2 and 3, may be integrated with other components. For example, all or a portion of the functionality provided by components 200 and/or 300 may be provided as a System-On-Chip (SOC), or the like.

FIG. 4 is a block diagram of multi-form factor configuration engine 401. Particularly, multi-form factor configuration engine 401 may include electronic circuits and/or program instructions that, upon execution, cause IHS 100 to perform a number of operation(s) and/or method(s) described herein.

In various implementations, program instructions for executing multi-form factor configuration engine 401 may be stored in memory 203. For example, engine 401 may include one or more standalone software applications, drivers, libraries, or toolkits, accessible via an Application Programming Interface (API) or the like. Additionally, or alternatively, multi-form factor configuration engine 401 may be included the IHS's OS.

In other embodiments, however, multi-form factor configuration engine 401 may be implemented in firmware and/or executed by a co-processor or dedicated controller, such as a Baseband Management Controller (BMC), or the like.

As illustrated, multi-form factor configuration engine 401 receives Graphical User Interface (GUI) input or feature 402, and produces GUI output or feature 403, in response to receiving and processing one or more or: display sensor data 406, hinge sensor data 407, and/or keyboard sensor data 408. Additionally, or alternatively, multi-form factor configuration engine 401 may produce touch control feature 404 and/or other commands 405.

In various embodiments, GUI input 402 may include one or more images to be rendered on display(s) 101/102, and/or one or more entire or partial video frames. Conversely, GUI output 403 may include one or more modified images (e.g., different size, color, position on the display, etc.) to be rendered on display(s) 101/102, and/or one or more modified entire or partial video frames.

For instance, in response to detecting, via display and/or hinge sensors 406/407, that IHS 100 has assumed a laptop posture from a closed or “off” posture, GUI OUT 403 may allow a full-screen desktop image, received as GUI IN 402, to be displayed first display 101 while second display 102 remains turned off or darkened. Upon receiving keyboard sensor data 408 indicating that keyboard 103 has been positioned over second display 102, GUI OUT 403 may produce a ribbon-type display or area 106 around the edge(s) of keyboard 103, for example, with interactive and/or touch selectable virtual keys, icons, menu options, pallets, etc. If keyboard sensor data 408 then indicates that keyboard 103 has been turned off, for example, GUI OUT 403 may produce an OSK on second display 102.

Additionally, or alternatively, touch control feature 404 may be produced to visually delineate touch input area 107 of second display 102, to enable its operation as a user input device, and to thereby provide an UI interface commensurate with a laptop posture. Touch control feature 404 may turn palm or touch rejection on or off in selected parts of display(s) 101/102. Also, GUI OUT 403 may include a visual outline displayed by second display 102 around touch input area 107, such that palm or touch rejection is applied outside of the outlined area, but the interior of area 107 operates as a virtual trackpad on second display 102.

Multi-form factor configuration engine 401 may also produce other commands 405 in response to changes in display posture and/or keyboard state or arrangement, such as commands to turn displays 101/102 on or off, enter a selected power mode, charge or monitor a status of an accessory device (e.g., docked in hinge 104), etc.

FIG. 5 is a flowchart of method 500 for configuring multi-form factor IHSs. In various embodiments, method 500 may be performed by multi-form factor configuration engine 401 under execution of processor 201. At block 501, method 500 includes identifying a display posture—that is, a relative physical arrangement between first display 101 and second display 102. For example, block 501 may use sensor data received from displays 101/102 and/or hinge 104 to distinguish among the various postures shown below.

At block 502, method 500 selects a UI feature corresponding to the identified posture. Examples of UI features include, but are not limited to: turning a display on or off; displaying a full or partial screen GUI; displaying a ribbon area; providing a virtual trackpad area; altering touch control or palm rejection settings; adjusting the brightness and contrast of a display; selecting a mode, volume, and/or or directionality of audio reproduction; etc.

At block 503, method 500 may detect the status of keyboard 103. For example, block 503 may determine that keyboard 103 is on or off, resting between two closed displays, horizontally sitting atop display(s) 101/102, or next to display(s) 101/102. Additionally, or alternatively, block 503 may determine the location or position of keyboard 103 relative to display 102, for example, using Cartesian coordinates. Additionally, or alternatively, block 503 may determine an angle between keyboard 103 and displays 101/102 (e.g., a straight angle if display 102 is horizontal, or a right angle if display 102 is vertical).

Then, at block 504, method 500 may modify the UI feature in response to the status of keyboard 103. For instance, block 504 may cause a display to turn on or off, it may change the size or position of a full or partial screen GUI or a ribbon area, it may change the size or location of a trackpad area with changes to control or palm rejection settings, etc. Additionally, or alternatively, block 504 may produce a new interface feature or remove an existing feature, associated with a display posture, in response to any aspect of the keyboard status meeting a selected threshold of falling within a defined range of values.

FIGS. 6A-C, 7A-J, 8A-D, and 9A-F illustrate examples of laptop, tablet, book, and display postures which may be detected by operation of block 501 of method 500 during execution of multi-form factor configuration engine 401 by IHS 100.

Particularly, FIGS. 6A-C show a laptop posture, where a first display surface of first display 101 is facing the user at an obtuse angle with respect to a second display surface of second display 102, and such that second display 102 is disposed in a horizontal position, with the second display surface facing up. In FIG. 6A, state 601 shows a user operating IHS 100 with a stylus or touch on second display 102. In FIG. 6B, state 602 shows IHS 100 with keyboard 103 positioned off the bottom edge or long side of second display 102, and in FIG. 6C, state 603 shows the user operating keyboard 103 atop second display 102.

FIGS. 7A-J show a tablet posture, where first display 101 is at a straight angle with respect to second display 102, such that first and second displays 101 and 102 are disposed in a horizontal position, with the first and second display surfaces facing up. Specifically, FIG. 7A shows state 701 where IHS 100 is in a side-by-side, portrait orientation without keyboard 103, FIG. 7B shows state 702 where keyboard 103 is being used off the bottom edges or short sides of display(s) 101/102, and FIG. 7C shows state 703 where keyboard 103 is located over both displays 101 and 102. In FIG. 7D, state 704 shows IHS 100 in a side-by-side, landscape configuration without keyboard 103, in FIG. 7E state 705 shows keyboard 103 being used off the bottom edge or long side of second display 102, and in FIG. 7F state 706 shows keyboard 103 on top of second display 102.

In FIG. 7G, state 707 shows first display 101 rotated around second display 102 via hinge 104 such that the display surface of second display 102 is horizontally facing down, and first display 101 rests back-to-back against second display 102, without keyboard 103; and in FIG. 7H, state 708 shows the same configuration, but with keyboard 103 placed off the bottom or long edge of display 102. In FIGS. 71 and 7J, states 709 and 710 correspond to states 707 and 708, respectively, but with IHS 100 in a portrait orientation.

FIG. 8A-D show a book posture, similar to the tablet posture of FIGS. 7A-J, but such that neither one of displays 101 or 102 is horizontally held by the user and/or such that the angle between the display surfaces of the first and second displays 101 and 102 is other than a straight angle. In FIG. 8A, state 801 shows dual-screen use in portrait orientation, in FIG. 8B state 802 shows dual-screen use in landscape orientation, in FIG. 8C state 803 shows single-screen use in landscape orientation, and in FIG. 8D state 804 shows single-screen use in portrait orientation.

FIGS. 9A-F show a display posture, where first display 100 is at an acute angle with respect to second display 102, and/or where both displays are vertically arranged in a portrait orientation. Particularly, in FIG. 9A state 901 shows a first display surface of first display 102 facing the user and the second display surface of second display 102 horizontally facing down, whereas in FIG. 9B state 902 shows the same configuration but with keyboard 103 used off the bottom edge or long side of display 101. In FIG. 9C, state 903 shows a display posture where display 102 props up display 101 in a stand configuration, and in FIG. 9D, state 904 shows the same configuration but with keyboard 103 used off the bottom edge or long side of display 101. In FIG. 9E, state 905 shows both displays 101 and 102 resting vertically or at display angle, and in FIG. 9F state 906 shows the same configuration but with keyboard 103 used off the bottom edge or long side of display 101.

It should be noted that the aforementioned postures, and their various respective keyboard states, are described for sake of illustration. In different embodiments, however, other postures and keyboard states may be used, for example, depending upon the type of hinge coupling the displays, the number of displays used, or other accessories. For instance, when IHS 100 is chargeable via a charging or docking station, the connector in the docking station may be configured to hold IHS 100 at angle selected to facility one of the foregoing postures (e.g., keyboard states 905 and 906).

FIGS. 10A-C illustrate a first example use-case of method 500 in the context of a laptop posture. In state 1000A of FIG. 10A, first display 101 shows primary display area 1001, keyboard 103 sits atop second display 102, and second display 102 provides UI features such as first ribbon area 1002 (positioned between the top long edge of keyboard 103 and hinge 104) and touch area 1003 (positioned below keyboard 103). As keyboard 103 moves up or down on the surface of display 102, ribbon area 1002 and/or touch area 1003 may dynamically move up or down, or become bigger or smaller, on second display 102. In some cases, when keyboard 103 is removed, a virtual OSK may be rendered (e.g., at that same location) on the display surface of display 102.

In state 1000B of FIG. 10B, in response to execution of method 500 by multi-form factor configuration engine 401, first display 101 continues to show main display area 1001, but keyboard 103 has been moved off of display 102. In response, second display 102 now shows secondary display area 1004 and also second ribbon area 1005. In some cases, second ribbon area 1005 may include the same UI features (e.g., icons, etc.) as also shown in area 1002, but here repositioned to a different location of display 102 nearest the long edge of keyboard 103. Alternatively, the content of second ribbon area 1005 may be different from the content of first ribbon area 1002.

In state 1000C of FIG. 100, during execution of method 500 by multi-form factor configuration engine 401, IHS 100 detects that physical keyboard 103 has been removed (e.g., out of wireless range) or turned off (e.g., low battery), and in response display 102 produces a different secondary display area 1006 (e.g., smaller than 1004), as well as OSK 1007.

FIGS. 11A-C illustrate a second example use-case of method 500 in the context of a tablet posture. In state 1100A of FIG. 11A, second display 102 has its display surface facing up, and is disposed back-to-back with respect to second display 102, as in states 709/710, but with keyboard 103 sitting atop second display 102. In this state, display 102 provides UI features such primary display area 1101 and first ribbon area 1102, positioned as shown. As keyboard 103 is repositioned up or down on the surface of display 102, display area 1101, first ribbon area 1102, and/or touch area 1103 may also be moved up or down, or made bigger or smaller, by multi-form factor configuration engine 401.

In state 1100B of FIG. 11B, keyboard 103 is detected off of the surface of display 102. In response, first display 101 shows modified main display area 1103 and modified ribbon area 1104. In some cases, modified ribbon area 1104 may include the same UI features as area 1102, but here repositioned to a different location of display 102 nearest the long edge of keyboard 103. Alternatively, the content of second ribbon area 1104 may be different from the content of first ribbon area 1102. In some cases, the content and size of modified ribbon area 1104 may be selected in response to a distance between keyboard 103 and display 102.

In state 1100C of FIG. 11C, during continued execution of method 500, multi-form factor configuration engine 401 detects that physical keyboard 103 has been removed or turned off, and in response display 102 produces yet another display area 1105 (e.g., larger than 1003 or 1002), this time without an OSK.

In various embodiments, the different UI behaviors discussed in the aforementioned use-cases may be set, at least in part, by policy and/or profile, and stored in a preferences database for each user. In this manner, UI features and modifications of blocks 502 and 504, such as whether touch input area 1003 is produced in state 1000A (and/or its size and position on displays 101/102), or such as whether ribbon area 1102 is produced in state 1100A (and/or its size and position on displays 101/102), may be configurable by a user.

FIGS. 12A-D illustrate a 360-hinge implementation, usable as hinge 104 in IHS 100, in four different configurations 1200A-D, respectively. Particularly, 360-hinge 104 may include a plastic, acrylic, polyamide, polycarbonate, elastic, and/or rubber coupling, with one or more internal support, spring, and/or friction mechanisms that enable a user to rotate displays 101 and 102 relative to one another, around the axis of 360-hinge 104.

Hinge configuration 1200A of FIG. 12A may be referred to as a closed posture, where at least a portion of a first display surface of the first display 101 is disposed against at least a portion of a second display surface of the second display 102, such that the space between displays 101/102 accommodates keyboard 103. When display 101 is against display 102, stylus or accessory 108 may be slotted into keyboard 103. In some cases, stylus 108 may have a diameter larger than the height of keyboard 103, so that 360-hinge 104 wraps around a portion of the circumference of stylus 108 and therefore holds keyboard 103 in place between displays 101/102.

Hinge configuration 1200B of FIG. 12B shows a laptop posture between displays 101/102. In this case, 360-hinge 104 holds first display 101 up, at an obtuse angle with respect to first display 101. Meanwhile, hinge configuration 1200C of FIG. 12C shows a tablet, book, or display posture (depending upon the resting angle and/or movement of IHS 100), with 360-hinge 104 holding first and second displays 101/102 at a straight angle (180°) with respect to each other. And hinge configuration 1200D of FIG. 12D shows a tablet or book configuration, with 360-hinge 104 holding first and second displays 101 and 102 at a 360° angle, with their display surfaces in facing opposite directions.

FIGS. 13A and 13B illustrate a jaws hinge implementation, usable as hinge 104 in IHS 100, in two different configurations 1300A and 1300B. Specifically, jaws hinge 104 has two rotation axes, parallel to each other, one axis for each respective one of displays 101/102. A solid bar element 104 between the two rotation axes may be configured to accommodate docking compartment 1301 for stylus 108, audio speaker(s) 1302 (e.g., monaural, stereo, a directional array), and one or more ports 1303 (e.g., an audio in/out jack).

Hinge configuration 1300A of FIG. 13A shows the laptop posture. In this case, jaws hinge 104 holds first display 101 up, at an obtuse angle with respect to second display 102. In contrast, hinge configuration 1300B of FIG. 13B shows a tablet or book posture, with jaws hinge 104 holding first and second displays 101 and 102 at a 360° angle with respect to each other, with keyboard 103 stored in between displays 101 and 102, in a back-to-back configuration, such that stylus 108 remains accessible to the user.

FIG. 14 illustrates accessory charging system 1400, with accessory wells 1301 and 1401 shown on hinge 104 that couples first display 101 to second display 102. In various embodiments, accessory wells 1301 and 1401 may be formed of molded or extruded plastic. In this example, accessory well 1301 is shaped to hold pen or stylus 108, and accessory well 1401 is shaped to hold earbud 109. In some implementations, wells 1301 and/or 1401 may include electrical terminals for charging a battery within the accessory, and/or to check a status of the accessory (e.g., presence, charge level, model or name, etc.).

FIG. 15 illustrates a yoga hinge implementation, usable as hinge 104 in IHS 100, in configuration 1500. Specifically, yoga hinge 104 comprises a plurality of metal cylinders or rods, with axes parallel to each other, held together by bracket 1503 and/or fabric 1501. In operation, bracket 1503 may include notches and/or detents configured to hold cylinders 1502 at predetermined positions corresponding to any available IHS posture.

FIGS. 16A-C illustrate a gear hinge implementation, usable as hinge 104 in IHS 100, in configurations 1600A-C. Specifically, configuration 1600A of FIG. 16A shows gear hinge 104 with bar 1603 having teeth or gears 1604 fabricated thereon, as IHS 100 begins to assume a laptop posture. Display 101 has teeth or gears 1601 alongside its bottom edge, whereas display 102 has teeth or gears 1602 alongside its top edge. Bracket(s) 1605 hold gears 1601 and/or 1602 against gear 1604, therefore provides two parallel rotation axes between displays 101 and 102.

Hinge configuration 1600B of FIG. 16B shows a closed posture. In this case, gear hinge 104 holds display 101 facing down, and display 102 is rotated 360° degrees with respect to display 101, so that its display surface faces up against display 101. In this configuration, keyboard 103 may sit under display 102, for example, to cause display 102 to rest at an angle when IHS 100 is placed in laptop posture. In some cases, keyboard 103 may be coupled to the back of display 102 using an accessory backpack or the like, as shown in FIG. 19.

Hinge configuration 1600C of FIG. 16C shows a tablet or book posture. In this case, gear hinge 104 holds display 102 facing up, and display 101 is rotated 360° degrees with respect to display 102, so that its display surface faces down against the horizontal plane. In this configuration, keyboard 103 rests between the back of display 101 and the back of display 102. In various embodiments, bar 1603 may be split into a plurality of segments or links, as shown in configurations 1600B and 1600C, to provide additional axes of rotation between displays 101 and 102, and to accommodate both keyboard options with different IHS thicknesses.

FIGS. 17A and 17B illustrate a slide hinge implementation, usable as hinge 104 in IHS 100, in various configurations. Specifically, in FIG. 17A, link 1701, held by first display bracket 1702 coupled to display 101, slides up and down slot 1704 of bracket 1703 coupled to display 102. In some cases, a locking mechanism may be employed to stably hold displays 101 and 102 in different postures, as link 1701 slides up and down and/or as display 101 rotates around display 102, such as the closed posture of configuration 1700A, the laptop posture of configuration 1700B in FIG. 17B, the tablet posture of configuration 1700C (back to FIG. 17A), or the book posture of configuration 1700D (also in FIG. 17A).

FIGS. 18A and 18B illustrate a folio case system in configurations 1800A and 1800B, according to some embodiments. Specifically, folio case 1801 may include a set of hard foldable sections or flaps wrapped in fabric and/or plastic, with snapping magnetic attachment points, for example, around the edge on the back of displays 101 and 102, and/or keyboard 103. In some cases, keyboard 103 may be removable from case 1801. Additionally, or alternatively, the presence and state of case 1801 may be detectable via sensors 303.

In configuration 1800A in FIG. 18A, displays 101 and 102 are in a laptop posture, and folio case 1801 holds keyboard 103 in a fixed position, off the bottom edge or long side of display 102, such that both displays 101 and 102 remain usable. Meanwhile, configuration 1800B of FIG. 18B shows a display posture (e.g., as in state 901), such that the display surface of display 102 is facing down against folio case 1802, and folio case 1802 holds keyboard 103 in at fixed location, off the bottom edge of display 101, and such that only display 101 is usable.

FIG. 19 illustrates accessory backpack system 1900. In some embodiments, the enclosure of display 102 may include notches 1903 configured to receive lip 1902 of tray 1901, which stays snapped in place until pulled by the user. Additionally, or alternatively, a spring-loaded ejection button may be used. In various configurations, tray 1901 may hold keyboard 103 or battery 110. Moreover, in some cases, the enclosure of display 102 may include electrical terminals usable to charge and/or obtain sensor information from accessories.

Context-Aware User Interface (UI)

In various embodiments, systems and methods described herein may provide a context-aware UI for IHS 100. For example, GUI elements such as ribbon area 106 and touch input area 107 may be selected, configured, modified, provided, or excluded based upon the context in which IHS 100 is operating.

For example, during operation of IHS 100, an application or window may occupy a part of a display (“single display window mode”), it may occupy an entire display (“max mode”), it may span across parts of the two displays (“dual display window mode”), or it may occupy both entire displays (“supermax mode”). Moreover, when in a laptop or tablet posture mode, for instance, a user may place a supported physical keyboard 103, totem (e.g., a DELL DIAL TOTEM), or another accessory on the surface of second display 102. Additionally, or alternatively, the user may bring up an OSK on second display 102.

Still during operation of IHS 100, the user may move keyboard 103 to different positions on the display surface of second display 102. Additionally, or alternatively, the user may close, open, minimize, or maximize an application or window. Additionally, or alternatively, the user may transition IHS 100 between different display postures.

In response to these, or other events, IHS 100 may select, render, modify, expand, reduce, and/or exclude various UI components such as: applications, OSKs, touch bars, touchpads, workspaces, taskbars, start menus, etc., in a context-aware manner. These context-aware operations may be performed, for example, based on active application, touchpad area, physical keyboard placement and area, totem placement (if any), etc.

For instance, IHS 100 may bring up, hide, resize an “f-row interface” comprising one or more of: a “system bar,” a “touch bar,” and an “activity bar;” as well as the contents (e.g., icons, keys, text, colors, images, suggestions, shortcuts, input areas, etc.) of each such bar. Additionally, or alternatively, IHS 100 may bring up, configure, hide, or resize OSKs, touchpad areas, scratch pad areas, or totem menus. Additionally, or alternatively, IHS 100 may reduce or increase desktop or workspace areas that span two displays, and it may move OS components, such as a taskbar and start menu, across displays 101 and 102.

In an embodiment, a user may manually configure one or more GUI components (e.g., f-row interface, touchpad, OSK, etc.) with a desired size and selected contents, and the user may also choose taskbar/start menu icon locations with posture-dependent, event-specific triggers and behaviors. In another embodiment, a software service may detect placement of keyboard 103, posture changes, user configuration changes (e.g., user brings up OSK mode), totem placed on display, active application, etc., and it may take automatic responsive actions. In some cases, second display 102 may display touch bar content that is selected based upon other content displayed on first display 101 (e.g., an active application).

FIGS. 20A and 20B are a flowchart of method 2000 for providing a context-aware UI. In some embodiments, method 2000 may be performed by multi-form factor configuration engine 401 under execution of processor 201. Particularly, method 2000 starts at block 2001.

At block 2002, method 2000 loads user configuration and/or preferences from saved configuration files 2003. For example, configuration files 2003 may be saved in a database and stored in memory storage devices 203/207. In various embodiments, configuration files 2003 may contain user and/or application-specific settings that control the behavior of GUI components such as, for example, touch bar 106 and touchpad 107, in response to selected events. For example, configuration files 2003 may prioritize the rendering of one or more sub-components of touch bar 106 (e.g., a system bar, a touch bar, or an activity bar) and/or one or more sub-components of touch input area 107 (e.g., a trackpad and one or more scratchpad areas), according to the user's personal preferences, depending upon the position of keyboard 103 on second display 102.

At block 2004, method 2000 waits for an event to be received from any of blocks 2005-2009. Specifically, block 2005 indicates when an application is open, closed, or resized, and block 2006 indicates when an OSK mode is selected or brought up by an application (also examples of GUI IN 402 inputs in FIG. 4). Block 2007 detects and identifies changes in display posture, for example, using a gyroscope, accelerometer, IMU, hinge sensor, etc.; whereas blocks 2008 and 2009 detect the presence, position, and status of keyboard 103, totem, or other accessory, including moving and removal events, for example, using display, hinge, and keyboard sensors (also examples of sensor data 406-408 of FIG. 4).

At block 2010, method 2000 determines a current posture of IHS 100 using data from blocks 2005-2009 by comparing the various current states of different IHS components to the corresponding states expected for each posture. Block 2011 determines whether: (i) the posture has changed; (ii) OSK mode has been brought up, closed, or changed, or (iii) keyboard 103 has been placed, moved, or removed.

If so, block 2012 may calculate and apply a new workspace or desktop area by resizing and/or closing applications and windows using OS-specific (e.g., WINDOWS) API-based graphics (GFX) commands. Block 2013 may calculate and apply new ribbon area bars and components, with selected sizes and at predetermined locations, using the API to generate f-row UI commands. Similarly, block 2014 may calculate and apply new touch input area components such as a touchpad and one or more strachpad(s), with selected sizes and at predetermined locations, using the API to generate touchpad UI commands. In some cases, method 2000 may also calculate and apply OS components at block 2015, such as a taskbar or start menu, with selected sizes and at predetermined locations, using the API to generate OS configuration commands. After any of blocks 2012-2015, control returns to block 2004.

At block 2016, method 2000 determines whether an application has been opened, moved, minimized, maximized, or super-maximized. If so, block 2017 may calculate and resize applications and windows using the API, and control returns to block 2004. At block 2018, method 2000 determines whether a totem has been placed, removed, or moved, or whether a totem menu selection event has occurred. If so, block 2019 may send a totem event notification to the OS and/or it may enable totem controls/using the API, and then control returns to block 2004. Otherwise, method 2000 ends at block 2020.

FIGS. 21A-C illustrate an example of a keyboard attachment and alignment system. In various embodiments, the keyboard attachment and alignment system of FIGS. 21A-C may enable keyboard 103 to be attached to second display 102 at predetermined locations (on the display surface, or on the back of display 102), and/or to be aligned on/off the surface of display 102, at predetermined locations. Moreover, display and/or hinge sensors 210 may be configured to determine which of a plurality of magnetic devices are presently engaged, so that the current position of keyboard 103 may be ascertained with respect to IHS 100, and such that selected UI features may be provided in response to the keyboard's position, for example, as discussed in block 2008 of FIG. 20.

Particularly, FIG. 21A illustrates an example of attachable keyboard 103 having magnetic devices 2009A, 2009B, 2009C, and 2009D symmetrically disposed along its short sides, at selected locations. Additionally, or alternatively, keyboard 103 may include magnetic devices 2009E and 2009F disposed alongside the top, long side of keyboard 103.

FIG. 21B illustrates an example of attachable keyboard 103 with stylus 108 coupled to stylus well 2105. In some implementations, stylus 108 may have a compressible tip mated to a hole in stylus well 2105 that is configured to mechanically hold stylus 108 in place alongside the long edge of keyboard 103. Moreover, stylus 108 may include one or more magnetic devices 2100A and 2100B.

FIG. 21C illustrates an example of second display 102 configured for an attachable keyboard 103. Particularly, display 102 includes magnetic devices 2103A, 2103B, 2103D, and 2103E, which correspond to magnetic devices 2009A, 2009B, 2009C, and 2009D on the bottom of keyboard 103, and which snap keyboard 103 into a predetermined place over the display surface of display 102, in a first position alongside the short side of display 102 that enables hinge 104 to close and to sandwich keyboard 103 between displays 101 and 102.

Additionally, or alternatively, display 102 may include magnetic devices 2103C and 2103F. In combination, magnetic devices 2103B, 2103C, 2103E, and 2103F, which correspond to magnetic devices 2009A, 2009B, 2009C, and 2009D of keyboard 103, snap keyboard 103 into place over the display surface of display 102, in a second position alongside the short side of display 102 that enables rendering of first UI feature 106 (e.g., ribbon area) and/or second UI feature 107 (e.g., touchpad).

Additionally, or alternatively, display 102 may include magnetic devices 2102A and 2102B, which correspond to magnetic devices 2009E and 2009F in keyboard 103 and/or magnetic devices 2100A and 2100B in stylus 108. In some cases, magnetic devices 2102A and 2102B may be configured to snap keyboard 103 to the long edge of display 102, outside of its display surface. Additionally, or alternatively, display 102 may include magnetic devices 2104A, 2104B, 2104C, and 2104D, which correspond to magnetic devices 2009A, 2009B, 2009C, and 2009D of keyboard 103, and cause keyboard 103 to snap to the back of display 102, for example, as part of accessory backpack system 1900 (FIG. 19).

In some cases, hinge 104 may also include stylus well 2106. As shown, stylus well 2106 may include at least one of magnetic devices 2101A and 2101B, corresponding to magnetic devices 2009E and 2009F in keyboard 103 and/or magnetic devices 2100A and 2100B in stylus 108. As such, magnetic devices 2101A and 2101B may be configured to hold keyboard 103 and/or stylus 108 in place when keyboard 103 is sandwiched between displays 101 and 102.

In various embodiments, the system(s) of FIG. 21 may be used during execution of method 2000 of FIG. 20 to provide a context-aware UI for IHS 100. For sake of illustration, FIGS. 22A-D illustrate ribbon area 106 and touch input area 107 UI components that may be selected, configured, modified, provided or excluded based upon the context in which IHS 100 is operating. All configurations 2200A-D show IHS 100 in laptop posture.

In FIG. 22A, configuration 2200A has keyboard 103 absent, such that OSK 2204 is rendered between ribbon area 106 and touch input area 107. In this implementation, ribbon area 106 includes an “f-row interface” including three components: system bar 2203A-B, touch bar 2202, and activity bar 2201A-B.

System bar 2203A-B may include context-independent icon strip 2203B, having controls to provide direct access selected hardware or system components such as, for example, microphone muting, audio output volume, display brightness, etc. In addition, system bar 2203A-B may include context-dependent icon strip 2203A that presents context-based UI features, such as word suggestions made dynamically and predictively as the user types individual letter caps on OSK 2204, etc.

Touch bar 2202 may include contextually-selected icons or shortcuts to actions or commands associated with an active application rendered, for example, on first display 101. For instance, in case IHS 100 is executing an email application, touch bar 2202 may include “compose,” “check,” “reply,” “reply all,” “forward,” “move,” and “delete” icons, or the like. Each icon, when selected by the user, may cause a corresponding UI command to be received and executed by the active application.

Activity bar 2203A-B may include any of a plurality of widgets or small-sized applications. For example, activity bar strip 2203A may display a horizontally scrollable list of contextually-selected images or photographs, and activity bar strip 2204 may display a media player with album images and/or audio reproduction controls.

Touch input area 107 includes three components: virtual touchpad 2205A, and scratchpad 2205B, and scratchpad 2205C. Particularly, virtual touchpad 2205A may include a rectangular region below OSK 2204, optionally delineated by a visual outline (e.g., lighter shading or borders), with palm rejection controls selected or optimized for finger touch. Meanwhile, lateral scratchpads 2205B-C may have palm rejection controls selected or optimized for stylus input (e.g., sketching, handwriting, etc.).

In FIG. 22B, configuration 2200B shows keyboard 103 atop second display 102 at a distance d₁ from hinge 104. In this case, ribbon area 106 includes only system bar 2203A-B. The rendering of system bar 2203A-B may be performed upon sensing of distance d₁ along the short side of second display 102, for example, as keyboard 103 is detected and/or aligned using a magnetic guide system (FIG. 21), or the like.

In some implementations, system bar 2203A-B may be selected when keyboard 103 is at position d₁ in response to it having been assigned a highest priority among other f-row bars, as stored in configuration file or preferences 2003. Still with respect to configuration 2200B, touch input area 107 includes the same three components as in configuration 2200A, but with different sizes and/or placement of virtual touchpad 2205D, and scratchpad 2205E, and scratchpad 2205F.

In FIG. 22C, configuration 2200C has keyboard 103 at a distance d₂>d₁ from hinge 104, for example, as the user physically moves keyboard 103 down to a lower position along the short side of second display 102 during operation of IHS 100. In this case, ribbon area 106 includes both system bar 2203A-B and touch bar 2202. The rendering of touch bar 2202 in addition to system bar 2203A-B may be performed upon sensing of distance d₂, and in response to touch bar 2202 having been assigned a second highest priority among other f-row bars. In configuration 2200C, touch input area 107 includes only virtual touchpad 2205G, within a modified or repositioned rectangular region on second display 102.

In FIG. 22D, configuration 2200D has keyboard 103 at a distance d₃>d₂ from hinge 104. In this case, ribbon area 106 includes all of system bar 2203A-B, touch bar 2202, and activity bar 2201A-B. The rendering of activity bar 2201A-B in addition to system bar 2203A-B and touch bar 2202 may be performed upon sensing of distance d₃, and in response to touch bar 2202 having been assigned a third highest priority among other f-row bars. In configuration 2200D, touch input area 107 is removed.

Conversely, if the user moves keyboard 103 position d₃ to position d₂, for example, the UI on second display 102 is modified from configuration 2200D to configuration 2200C, and activity bar 2201A-B is removed from ribbon area 106, and touchpad 2205D is provided. Accordingly, as keyboard 103 is moved up or down the display surface of second display 102, ribbon area 106 and touch input area 107 may be modified dynamically to accommodate the graphical presentation of contextual information and controls, in order of priority or rank.

In various embodiments, a context-aware UI for IHS 100 may include OS-specific features, as discussed in blocks 2012 and 2015 of FIG. 20. In that regard, FIG. 23A depicts configuration 2300A, where first display 101 shows an application window and OS taskbar (or start menu) 2301, and second display 102 shows ribbon area 106, until the user removes keyboard 103 from the display surface of second display 102. OS taskbar 2301 may generally assumes the form of a long strip along one edge of display 101, and includes various icons which correspond to the windows open within an application, to facilitate switching between programs or windows, “pinning” programs or files so that they can be accessed quickly, and/or providing a notification area, which uses interactive icons to display real-time information about the state of IHS 100. In response to a keyboard removal event, FIG. 23B depicts configuration 2300B where second display 102 renders at least a portion of the application window (here in “supermax mode”), with the OS taskbar moved to position 2302 on second display 102.

Additionally, or alternatively, a context-aware UI for IHS 100 may include keyboard-initiated UI features, as shown in FIG. 24. In this implementation, when in configuration 2400, button 2401 on keyboard 103 may be configured to invoke and dismiss ribbon area 106 on second display 2402. In some cases, ribbon area 106 may include one or more icons representing one or more keys absent from keyboard 103. Additionally, or alternatively, when different types of keyboards 103 with different layouts are used (e.g., different languages, with application-specific keys, etc.), ribbon area 106 may include one or more icons particular to the type of keyboard 103.

It should be understood that various operations described herein may be implemented in software executed by logic or processing circuitry, hardware, or a combination thereof. The order in which each operation of a given method is performed may be changed, and various operations may be added, reordered, combined, omitted, modified, etc. It is intended that the invention(s) described herein embrace all such modifications and changes and, accordingly, the above description should be regarded in an illustrative rather than a restrictive sense.

Although the invention(s) is/are described herein with reference to specific embodiments, various modifications and changes can be made without departing from the scope of the present invention(s), as set forth in the claims below. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of the present invention(s). Any benefits, advantages, or solutions to problems that are described herein with regard to specific embodiments are not intended to be construed as a critical, required, or essential feature or element of any or all the claims.

Unless stated otherwise, terms such as “first” and “second” are used to arbitrarily distinguish between the elements such terms describe. Thus, these terms are not necessarily intended to indicate temporal or other prioritization of such elements. The terms “coupled” or “operably coupled” are defined as connected, although not necessarily directly, and not necessarily mechanically. The terms “a” and “an” are defined as one or more unless stated otherwise. The terms “comprise” (and any form of comprise, such as “comprises” and “comprising”), “have” (and any form of have, such as “has” and “having”), “include” (and any form of include, such as “includes” and “including”) and “contain” (and any form of contain, such as “contains” and “containing”) are open-ended linking verbs. As a result, a system, device, or apparatus that “comprises,” “has,” “includes” or “contains” one or more elements possesses those one or more elements but is not limited to possessing only those one or more elements. Similarly, a method or process that “comprises,” “has,” “includes” or “contains” one or more operations possesses those one or more operations but is not limited to possessing only those one or more operations. 

The invention claimed is:
 1. An Information Handling System (IHS), comprising: a processor; and a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution by the processor, cause the IHS to: identify an arrangement of a second display relative to a first display; identify a position of a keyboard relative to the second display; determine that the keyboard is placed atop a display surface of the second display; and modify a Graphical User Interface (GUI) provided by the second display in response to: (i) the arrangement; and (ii) the position, at least in part, by rendering a first bar on the second display along the keyboard.
 2. The IHS of claim 1, wherein the arrangement is identified as a laptop posture, wherein the first display is at an obtuse angle with respect to the second display, and wherein the second display is in a horizontal position with a display surface facing up.
 3. The IHS of claim 1, wherein the arrangement is identified as a tablet posture, wherein the first display is at a straight angle with respect to the second display, and wherein the first and second displays are disposed in a horizontal position with first and second display surfaces facing up.
 4. The IHS of claim 1, wherein the arrangement is identified as a book posture, wherein a first display surface of the first display is facing up, and wherein a back surface of the first display is against a second display surface of the second display.
 5. The IHS of claim 1, wherein the arrangement is identified as a display posture, wherein: (a) the first display is at an acute angle with respect to the second display; or (b) a first display surface of the first display is at a straight or obtuse angle with respect to a second display surface of the second display, and the first and second displays are at a right angle with respect to a horizontal surface.
 6. The IHS of claim 1, wherein the program instructions, upon execution, further cause the IHS to determine that the keyboard is being placed above the second display, and wherein modifying the GUI comprises: resizing an application on the second display, or moving the application from the second display to the first display.
 7. The IHS of claim 1, wherein the program instructions, upon execution, further cause the IHS to identify a context of an application being executed by the IHS, wherein modifying the GUI comprises adding a second bar to the first bar, and wherein contents of the second bar are selected based upon the context.
 8. The IHS of claim 1, wherein the program instructions, upon execution, further cause the IHS to determine that the keyboard is being moved from a first position on the display surface to a second position on the display surface, and wherein modifying the GUI comprises re-rendering the first bar at different locations on the second display as the keyboard moves.
 9. The IHS of claim 1, wherein the program instructions, upon execution, further cause the IHS to determine that the keyboard is being moved from a higher position on the display surface to a lower position on the display surface, and wherein modifying the GUI comprises dynamically adding a second bar to the first bar.
 10. The IHS of claim 1, wherein the program instructions, upon execution, further cause the IHS to determine that the keyboard is being moved from a lower position on the display surface to a higher position on the display surface, and wherein modifying the GUI comprises dynamically removing the second bar.
 11. The IHS of claim 1, wherein the program instructions, upon execution, further cause the IHS to determine that the keyboard is being removed from the second display surface, and wherein modifying the GUI comprises moving or expanding an application window from the first display to the second display.
 12. The IHS of claim 11, wherein modifying the GUI comprises moving an Operating System (OS) taskbar from the first display to the second display.
 13. The IHS of claim 1, wherein the program instructions, upon execution, further cause the IHS to determine that the keyboard is off of a display surface of the second display, and wherein modifying the GUI comprises rendering a first bar alongside an edge of the second display in response to a selected key being pressed on the keyboard.
 14. The IHS of claim 1, wherein the program instructions, upon execution, further cause the IHS to: determine that a key is absent from the keyboard; and render an image corresponding to the key on the second display.
 15. The IHS of claim 1, wherein modifying the GUI further comprises providing a virtual touchpad on a rectangular portion of a display surface of the second display below the keyboard.
 16. The IHS of claim 15, wherein modifying the GUI further comprises providing a scratch pad area below the keyboard and next to the touch input area.
 17. The IHS of claim 15, wherein the program instructions, upon execution, further cause the IHS to determine that the keyboard is being moved from a higher position on the display surface to a lower position on the display surface, and wherein modifying the GUI further comprises reducing the rectangular portion as the keyboard moves.
 18. A method, comprising: identifying an arrangement of a second display relative to a first display; identifying a position of a keyboard relative to the second display; determining that the keyboard is placed atop a display surface of the second display; and modifying a Graphical User Interface (GUI) provided by the second display in response to: (i) the arrangement; and (ii) the position, at least in part, by rendering a bar on the second display along the keyboard.
 19. A hardware memory device having program instructions stored thereon that, upon execution by a processor of an Information Handling System (IHS), cause the IHS to: identify an arrangement of a second display relative to a first display; identify a position of a keyboard relative to the second display; determine that the keyboard is placed atop a display surface of the second display; and modify a Graphical User Interface (GUI) provided by the second display in response to: (i) the arrangement; and (ii) the position, at least in part, by rendering a bar on the second display along the keyboard. 